psqlODBC 8.01.0105 Development snapshot

psqlODBC 8.01.0105 Development snapshot

am 18.12.2005 21:20:49 von Ludek Finstrle

Hello,

I announce new development snapshot with this informations:

Release Name: psqlodbc 8.01.0105

Notes:
This is 8.01.0105 development snapshot with one stability fix two
feature changes and one change which could be problematic in worst case.

We appriciate when you test this new release. Please drop us a note
in pgsql-odbc mailing list if it's ok or not.

It contains only psqlodbca.dll and psqlodbcw.dll.
You can install it only over some installed release version with
additional DLLs.


Changes:
1) psqlodbc-cancel_abort.diff
thie may fix problem with rollback aborted queries
this is the patch we don't know if it's fully ok (it may be)
2) psqlodbc-columns_pg.diff
SQLColumns or SQLColAttribute may return bad answer when Show system tables is turned off
3) psqlodbc-configdsn_delim.diff
this adds support for ; delimited options in ConfigDSN
4) psqlodbc-limit_bind_param.diff
it fixes problem with binding parameters and SQLCancel without SQLFreeStmt

Bug reports are welcome.

Regards,

Luf

---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match

Re: psqlODBC 8.01.0105 Development snapshot

am 19.12.2005 00:20:21 von alejandro.dburne

------=_Part_10556_20918178.1134948021770
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

2005/12/18, Ludek Finstrle :
>
> Hello,
>
> I announce new development snapshot with this informations:
>
> Release Name: psqlodbc 8.01.0105
>
> Notes:
> This is 8.01.0105 development snapshot with one stability fix two
> feature changes and one change which could be problematic in worst case.
>
> We appriciate when you test this new release. Please drop us a note
> in pgsql-odbc mailing list if it's ok or not.
>
> It contains only psqlodbca.dll and psqlodbcw.dll.
> You can install it only over some installed release version with
> additional DLLs.
>
>
> Changes:
> 1) psqlodbc-cancel_abort.diff
> thie may fix problem with rollback aborted queries
> this is the patch we don't know if it's fully ok (it may be)
> 2) psqlodbc-columns_pg.diff
> SQLColumns or SQLColAttribute may return bad answer when Show system
> tables is turned off
> 3) psqlodbc-configdsn_delim.diff
> this adds support for ; delimited options in ConfigDSN
> 4) psqlodbc-limit_bind_param.diff
> it fixes problem with binding parameters and SQLCancel without
> SQLFreeStmt
>
> Bug reports are welcome.
>
> Regards,
>
> Luf
>
> Where to download?

Ale

------=_Part_10556_20918178.1134948021770
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

2005/12/18, Ludek Finstrle <luf@pzkagi=
s.cz
>:

mail_quote" style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt=
0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,

  I announce new development snapshot with this inf=
ormations:

Release Name: psqlodbc 8.01.0105

Notes:
This is=
8.01.0105 development snapshot with one stability fix two
feature chang=
es and one change which could be problematic in worst case.


We appriciate when you test this new release. Please drop us a note=

in pgsql-odbc mailing list if it's ok or not.

It contains only p=
sqlodbca.dll and psqlodbcw.dll.
You can install it only over some instal=
led release version with

additional DLLs.


Changes:
1) psqlodbc-cancel_abort.diff r>   thie may fix problem with rollback aborted queries
 =
  this is the patch we don't know if it's fully ok (it may be)
2) p=
sqlodbc-columns_pg.diff

   SQLColumns or SQLColAttribute may return bad answer when S=
how system tables is turned off
3) psqlodbc-configdsn_delim.diff
&nbs=
p;  this adds support for ; delimited options in ConfigDSN
4) psqlo=
dbc-limit_bind_param.diff

   it fixes problem with binding parameters and SQLCancel wit=
hout SQLFreeStmt

Bug reports are welcome.

Regards,

Luf=


Where to download?

Ale


------=_Part_10556_20918178.1134948021770--

Re: psqlODBC 8.01.0105 Development snapshot

am 19.12.2005 02:24:49 von Peter Eisentraut

Ludek Finstrle wrote:
> I announce new development snapshot with this informations:
> Release Name: psqlodbc 8.01.0105

Um, it might be nice of you create a CVS tag for snapshot releases (as
was done in the past) and if you provided the source code somewhere.
This is "open source" software after all. And making binary only
releases might also be considered a license violation.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Re: psqlODBC 8.01.0105 Development snapshot

am 19.12.2005 08:55:43 von Ludek Finstrle

> > Release Name: psqlodbc 8.01.0105
> Where to download?

I'm sorry, I forgot. You can download it from pgfoundry.org:

http://pgfoundry.org/frs/?group_id=1000125

Regards,

Luf

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Re: psqlODBC 8.01.0105 Development snapshot

am 19.12.2005 09:03:57 von Ludek Finstrle

> > I announce new development snapshot with this informations:
> > Release Name: psqlodbc 8.01.0105
>
> Um, it might be nice of you create a CVS tag for snapshot releases (as

It's not compiled from CVS only. There is some patches which isn't
commited yet. May I still create CVS tag?

> was done in the past) and if you provided the source code somewhere.
> This is "open source" software after all. And making binary only
> releases might also be considered a license violation.

I think all patches goes through pgsql-odbc mailing list so if anyone
would get the source he can. I don't think over a license violation.
If you think it's license violation I have to remove older dev
snapshots (it's too time consuming to get source for it) and I'll add
source code for latest dev snapshot).

What's your opinion?

Thanks

Luf

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq

Re: psqlODBC 8.01.0105 Development snapshot

am 19.12.2005 09:48:54 von Dave Page

=20

> -----Original Message-----
> From: pgsql-odbc-owner@postgresql.org=20
> [mailto:pgsql-odbc-owner@postgresql.org] On Behalf Of Ludek Finstrle
> Sent: 19 December 2005 08:04
> To: Peter Eisentraut
> Cc: pgsql-odbc@postgresql.org
> Subject: Re: [ODBC] psqlODBC 8.01.0105 Development snapshot
>=20
> > > I announce new development snapshot with this informations:
> > > Release Name: psqlodbc 8.01.0105
> >=20
> > Um, it might be nice of you create a CVS tag for snapshot=20
> releases (as=20
>=20
> It's not compiled from CVS only. There is some patches which isn't
> commited yet. May I still create CVS tag?

No. CVS tags must match what is actually released.

> > was done in the past) and if you provided the source code=20
> somewhere.
> > This is "open source" software after all. And making binary only=20
> > releases might also be considered a license violation.
>=20
> I think all patches goes through pgsql-odbc mailing list so if anyone
> would get the source he can. I don't think over a license violation.
> If you think it's license violation I have to remove older dev
> snapshots (it's too time consuming to get source for it) and I'll add
> source code for latest dev snapshot).
>=20
> What's your opinion?

I think Peter's being a little over cautious. There have been psqlODBC
snapshots released without source releases right back to when Byron was
maintaining it years ago. They are 'official' project snapshots, built
for testing purposes by the primary copyright holders (PGDG) and
released onto the project site which hosts the source repository. AFAICR
I'm the only one who ever did release source tarballs with snapshots.

The easy way to be sure though, is to just zip up the source tree and
upload it with the binaries, or better yet, build a tarball on a Unix
box or in Msys and upload that.

Regards, Dave.

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend

Re: psqlODBC 8.01.0105 Development snapshot

am 19.12.2005 13:59:53 von Ludek Finstrle

> > > was done in the past) and if you provided the source code
> > somewhere.
> > > This is "open source" software after all. And making binary only
> > > releases might also be considered a license violation.
> >
> > I think all patches goes through pgsql-odbc mailing list so if anyone
> > would get the source he can. I don't think over a license violation.
> > If you think it's license violation I have to remove older dev
> > snapshots (it's too time consuming to get source for it) and I'll add
> > source code for latest dev snapshot).
> >
> > What's your opinion?
>
> I think Peter's being a little over cautious. There have been psqlODBC
> snapshots released without source releases right back to when Byron was
> maintaining it years ago. They are 'official' project snapshots, built
> for testing purposes by the primary copyright holders (PGDG) and
> released onto the project site which hosts the source repository. AFAICR
> I'm the only one who ever did release source tarballs with snapshots.

Ok. I don't remove old snapshots. I put source code for dev snapshot
8.01.0105 when I come at home. I add source code tarball in future with
dev snapshots.

Regards,

Luf

---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?

http://archives.postgresql.org

Re: psqlODBC 8.01.0105 Development snapshot

am 19.12.2005 20:35:13 von Ludek Finstrle

> I announce new development snapshot with this informations:
>
> Release Name: psqlodbc 8.01.0105

I upload source code for 8.01.0105 few minutes ago.

Luf

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq